brain-onboard: stop installing team-member-memory at onboarding - #135
Merged
Kyra Richards (kyra-cpu) merged 1 commit intoJun 12, 2026
Merged
Conversation
Step 1.5 no longer fetches team-member-memory from the library onto customer VMs. The use case is hidden from the public catalog while it's reworked, and onboarding must never pull a hidden use case onto a customer VM. corpus-search is still fetched if absent, exactly as before. No other behavior changed. Bumps install-config to 2.3.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Step 1.5 of brain-onboard no longer fetches and installs
team-member-memoryfrom the library onto customer VMs.corpus-searchis still fetched if absent, exactly as before. install-config bumped to 2.3.0 with a changelog entry. No other behavior changed.Why
team-member-memoryis hidden from the public catalog while it's reworked (.use-case-library/catalog.jsonexcluded[]: "Active rework in flight"), and onboarding must never pull a hidden use case onto a customer VM. Shipping this also stops fresh onboards from installing the version whose Neon→daemon-DB resolver swap is still pending in #134 — fresh installs of that version were what demanded theNEON_DATABASE_URLprod secret in the 2026-06-11 incident.Notes
🤖 Generated with Claude Code